projects / gtk4.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4acbcf9) | patch
GtkSearchEngine: Use all search engines
authorMatthias Clasen <mclasen@redhat.com>
Fri, 1 May 2015 19:34:08 +0000 (15:34 -0400)
committerMatthias Clasen <mclasen@redhat.com>
Fri, 1 May 2015 19:46:47 +0000 (15:46 -0400)
commit05bde9d8dd539af36ed99cf3a2b00933d15562b0
tree170d9ba7e01e9a512df46f2f70cf300e5b5a15d9tree | snapshot
parent4acbcf9e97d7aab6de28603dea291aa08749e982commit | diff
GtkSearchEngine: Use all search engines

Just using tracker does not work well if you are searching in
non-indexed locations, such as git checkouts or network mounts.

Ideally, we'd decide the 'best' engine to use for each location.
Since that is not easy to do, just run them in parallel for now,
which is the same strategy that nautilus uses.
gtk/gtksearchengine.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.